Skip to content

Accessibility statement based on moodle.org statement #1364

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 10, 2025
Merged

Conversation

wildgirl
Copy link
Contributor

Accessibility statement based on moodle.org Accessibility statement (MDLSITE-8064)

Copy link

netlify bot commented May 26, 2025

Deploy Preview for moodledevdocs ready!

Name Link
🔨 Latest commit c289fbc
🔍 Latest deploy log https://app.netlify.com/projects/moodledevdocs/deploys/68482f9e784f84000825c121
😎 Deploy Preview https://deploy-preview-1364--moodledevdocs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@wildgirl wildgirl requested review from a team as code owners May 26, 2025 12:45
@andrewnicols andrewnicols requested a review from junpataleta May 27, 2025 00:17
@junpataleta
Copy link
Collaborator

Thanks, @wildgirl. I think that it would be good to emphasise that the dev docs site is powered by Docusaurus, and while Docusaurus does not specify a specific WCAG conformance level, we aim to meet WCAG Level 2.2 AA conformance across the site.

It may also be worth noting that moodledev.io is driven by community contributions, and that we strive to the best of our ability to ensure that the contributions are accessible.

For example:

At Moodle, we are committed to ensuring that the Moodle Developer Resource, powered by Docusaurus, is accessible to all users, including those with disabilities. While the Docusaurus framework does not specify a particular level of Web Content Accessibility Guidelines (WCAG) conformance, our goal is to meet WCAG 2.2 Level AA standards across our documentation site.

The Moodle Developer Resource is built and maintained through community contributions, reflecting the collective expertise and dedication of Moodle developers worldwide.

As part of this effort, we strive to:

  • Provide clear, structured, and easy-to-navigate content.
  • Encourage contributors to follow accessibility best practices when submitting documentation.
  • Ensure compatibility with assistive technologies, including screen readers and keyboard navigation.
  • Use accessible colour, typography, and media elements.
  • Continuously review and improve the site's accessibility based on feedback and best practices.

In the What to do if you cannot access any part of this website section, it may also be worth mentioning that users encountering accessibility issues/barriers may also raise an issue in our Github repository.

I hope this helps!

@sarjona sarjona force-pushed the wildgirl-patch-1 branch from 7620b6e to ba76172 Compare June 10, 2025 12:55
… of this website' and 'Questions, comments and suggestions'
Copy link
Member

@sarjona sarjona left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @wildgirl!
Thanks for improving the content of this page and including Jun's suggestions :-)
The patch looks great so I'm happy to approve it ;-)

@sarjona sarjona added this pull request to the merge queue Jun 10, 2025
Merged via the queue into main with commit 56d3654 Jun 10, 2025
7 checks passed
@sarjona sarjona deleted the wildgirl-patch-1 branch June 10, 2025 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants